Add network info cleanup and missing file retry logic#706
Merged
EhabY merged 3 commits intocoder:mainfrom Dec 31, 2025
Merged
Conversation
- Clean up network info files older than 1 hour when monitoring starts - Search for new SSH process after 5 consecutive file read failures
EhabY
force-pushed
the
delete-old-network-info-files
branch
from
b43d8f1 to
dba73e1
Compare
johnstcn
reviewed
Dec 30, 2025
johnstcn
approved these changes
Dec 30, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
<pid>.jsonfiles in the network info directory on monitor start (files older than 1 hour)Details
Network info files (
<basePath>/net/<pid>.json) are created by the Coder CLI and persist after processes terminate. This adds automatic cleanup of files not modified in the last hour.Previously, if the network info file was missing (e.g., deleted or never created), the monitor would log errors indefinitely without attempting to find a new process. Now it behaves consistently with stale file detection - after 5 failures (with delays), it searches for a new SSH process.
Closes #51